Skip to content

update github.com/DataDog/ebpf-manager to v0.8.3 - #55262

Merged
gh-worker-dd-mergequeue-cf854d[bot] merged 1 commit into
mainfrom
bryce.kahle/ebpf-manager-v083
Aug 26, 2026
Merged

update github.com/DataDog/ebpf-manager to v0.8.3#55262
gh-worker-dd-mergequeue-cf854d[bot] merged 1 commit into
mainfrom
bryce.kahle/ebpf-manager-v083

Conversation

@brycekahle

@brycekahle brycekahle commented Aug 21, 2026

Copy link
Copy Markdown
Member

What does this PR do?

update github.com/DataDog/ebpf-manager to v0.8.3

Motivation

Fix data race. See DataDog/ebpf-manager#285

Describe how you validated your changes

Additional Notes

@brycekahle brycekahle added changelog/no-changelog No changelog entry needed qa/done QA done before merge and regressions are covered by tests labels Aug 21, 2026
@dd-octo-sts dd-octo-sts Bot added the internal Identify a non-fork PR label Aug 21, 2026
@github-actions github-actions Bot added the short review PR is simple enough to be reviewed quickly label Aug 21, 2026
@datadog-prod-us1-5

datadog-prod-us1-5 Bot commented Aug 21, 2026 •
edited by datadog-prod-us1-4 Bot
Loading

Copy link
Copy Markdown
Contributor

🎯 Code Coverage (details)
• Patch Coverage: 100.00%
• Overall Coverage: 52.63% (+0.01%)

This comment will be updated automatically if new data arrives.
🔗 Commit SHA: 0f6d164 | Docs | View more details | Give us feedback!

@dd-octo-sts

dd-octo-sts Bot commented Aug 21, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

Files inventory check summary

File checks results against ancestor aefb652e:

Results for datadog-agent_7.84.0~devel.git.507.0f6d164.pipeline.133492325-1_amd64.deb:

No change detected

Results for datadog-iot-agent_7.84.0~devel.git.507.0f6d164.pipeline.133492325-1_amd64.deb:

No change detected

@dd-octo-sts

dd-octo-sts Bot commented Aug 21, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

Static quality checks

✅ Please find below the results from static quality gates
Comparison made with ancestor aefb652
📊 Static Quality Gates Dashboard
🔗 SQG Job

Successful checks

Info

Quality gate Change Size (prev → curr → max)
✅ agent_rpm_arm64_fips +4.0 KiB (0.00% increase, -0.59% of buffer) 693.154 → 693.158 → 693.820
✅ agent_suse_arm64_fips +4.0 KiB (0.00% increase, -0.59% of buffer) 693.154 → 693.158 → 693.820
30 successful checks with minimal change (< 2 KiB)
Quality gate Current Size
✅ agent_deb_amd64 761.262 MiB
✅ agent_deb_amd64_fips 714.005 MiB
✅ agent_heroku_amd64 312.914 MiB
✅ agent_rpm_amd64 761.246 MiB
✅ agent_rpm_amd64_fips 713.989 MiB
✅ agent_rpm_arm64 737.128 MiB
✅ agent_suse_amd64 761.246 MiB
✅ agent_suse_amd64_fips 713.989 MiB
✅ agent_suse_arm64 737.128 MiB
✅ docker_agent_amd64 819.833 MiB
✅ docker_agent_arm64 820.802 MiB
✅ docker_agent_jmx_amd64 1010.746 MiB
✅ docker_agent_jmx_arm64 1000.494 MiB
✅ docker_cluster_agent_amd64 211.439 MiB
✅ docker_cluster_agent_arm64 224.522 MiB
✅ docker_cws_instrumentation_amd64 7.443 MiB
✅ docker_cws_instrumentation_arm64 6.877 MiB
✅ docker_dogstatsd_amd64 39.529 MiB
✅ docker_dogstatsd_arm64 37.623 MiB
✅ docker_host_profiler_amd64 306.851 MiB
✅ docker_host_profiler_arm64 318.179 MiB
✅ dogstatsd_deb_amd64 30.274 MiB
✅ dogstatsd_deb_arm64 28.287 MiB
✅ dogstatsd_rpm_amd64 30.274 MiB
✅ dogstatsd_suse_amd64 30.274 MiB
✅ iot_agent_deb_amd64 46.540 MiB
✅ iot_agent_deb_arm64 43.181 MiB
✅ iot_agent_deb_armhf 43.987 MiB
✅ iot_agent_rpm_amd64 46.541 MiB
✅ iot_agent_suse_amd64 46.540 MiB

@cit-pr-commenter-54b7da

cit-pr-commenter-54b7da Bot commented Aug 21, 2026 •
edited
Loading

Copy link
Copy Markdown

Regression Detector

Regression Detector Results

Metrics dashboard
Target profiles
Job ID: 46965766-0f2d-4c20-b978-9e6f0e47bb73

Baseline: e2f380d
Comparison: 8e15523
Diff

Optimization Goals: ✅ No significant changes detected

Fine details of change detection per experiment

perf experiment goal Δ mean % Δ mean % CI trials links
➖ quality_gate_logs % cpu utilization +1.86 [+0.99, +2.73] 1 Logs bounds checks dashboard
➖ dsd_uds_10mb_3k_timestamped_contexts_cpu % cpu utilization +0.79 [+0.55, +1.02] 1 Logs
➖ quality_gate_metrics_logs memory utilization +0.71 [+0.48, +0.93] 1 Logs bounds checks dashboard
➖ dsd_uds_10mb_3k_timestamped_contexts_memory memory utilization +0.17 [-0.05, +0.38] 1 Logs
➖ quality_gate_security_idle memory utilization +0.12 [+0.07, +0.17] 1 Logs bounds checks dashboard
➖ quality_gate_security_mean_fs_load memory utilization +0.03 [-0.01, +0.06] 1 Logs bounds checks dashboard
➖ quality_gate_security_no_fs_load memory utilization -0.06 [-0.14, +0.02] 1 Logs bounds checks dashboard
➖ quality_gate_private_action_runner memory utilization -0.09 [-0.21, +0.03] 1 Logs bounds checks dashboard
➖ quality_gate_idle memory utilization -0.22 [-0.26, -0.17] 1 Logs bounds checks dashboard
➖ quality_gate_idle_all_features memory utilization -0.45 [-0.49, -0.42] 1 Logs bounds checks dashboard

Bounds Checks: ✅ Passed

perf experiment bounds_check_name replicates_passed observed_value links
✅ quality_gate_idle intake_connections 10/10 4 = 4 bounds checks dashboard
✅ quality_gate_idle memory_usage 10/10 172.99MiB ≤ 178MiB bounds checks dashboard
✅ quality_gate_idle total_bytes_received 10/10 745.81KiB ≤ 819.20KiB bounds checks dashboard
✅ quality_gate_idle_all_features intake_connections 10/10 4 = 4 bounds checks dashboard
✅ quality_gate_idle_all_features memory_usage 10/10 518.85MiB ≤ 538MiB bounds checks dashboard
✅ quality_gate_idle_all_features total_bytes_received 10/10 1.14MiB ≤ 1.25MiB bounds checks dashboard
✅ quality_gate_logs intake_connections 10/10 18 ≤ 40 bounds checks dashboard
✅ quality_gate_logs memory_usage 10/10 211.22MiB ≤ 229MiB bounds checks dashboard
✅ quality_gate_logs missed_bytes 10/10 0B = 0B bounds checks dashboard
✅ quality_gate_logs total_bytes_received 10/10 263.53MiB ≤ 292MiB bounds checks dashboard
✅ quality_gate_metrics_logs cpu_usage 10/10 363.64 ≤ 2000 bounds checks dashboard
✅ quality_gate_metrics_logs intake_connections 10/10 19 ≤ 40 bounds checks dashboard
✅ quality_gate_metrics_logs memory_usage 10/10 423.58MiB ≤ 453MiB bounds checks dashboard
✅ quality_gate_metrics_logs missed_bytes 10/10 0B = 0B bounds checks dashboard
✅ quality_gate_metrics_logs total_bytes_received 10/10 0.94GiB ≤ 1.04GiB bounds checks dashboard
✅ quality_gate_private_action_runner memory_usage 10/10 72.17MiB ≤ 76MiB bounds checks dashboard
✅ quality_gate_security_idle cpu_usage 10/10 28.87 ≤ 100 bounds checks dashboard
✅ quality_gate_security_idle memory_usage 10/10 323.18MiB ≤ 335MiB bounds checks dashboard
✅ quality_gate_security_mean_fs_load cpu_usage 10/10 66.64 ≤ 200 bounds checks dashboard
✅ quality_gate_security_mean_fs_load memory_usage 10/10 300.94MiB ≤ 314MiB bounds checks dashboard
✅ quality_gate_security_no_fs_load cpu_usage 10/10 22.16 ≤ 100 bounds checks dashboard
✅ quality_gate_security_no_fs_load memory_usage 10/10 308.76MiB ≤ 343MiB bounds checks dashboard

Explanation

Confidence level: 90.00%
Effect size tolerance: |Δ mean %| ≥ 5.00%

Performance changes are noted in the perf column of each table:

  • ✅ = significantly better comparison variant performance
  • ❌ = significantly worse comparison variant performance
  • ➖ = no significant change in performance

A regression test is an A/B test of target performance in a repeatable rig, where "performance" is measured as "comparison variant minus baseline variant" for an optimization goal (e.g., ingress throughput). Due to intrinsic variability in measuring that goal, we can only estimate its mean value for each experiment; we report uncertainty in that value as a 90.00% confidence interval denoted "Δ mean % CI".

For each experiment, we decide whether a change in performance is a "regression" -- a change worth investigating further -- if all of the following criteria are true:

  1. Its estimated |Δ mean %| ≥ 5.00%, indicating the change is big enough to merit a closer look.

  2. Its 90.00% confidence interval "Δ mean % CI" does not contain zero, indicating that if our statistical model is accurate, there is at least a 90.00% chance there is a difference in performance between baseline and comparison variants.

  3. Its configuration does not mark it "erratic".

CI Pass/Fail Decision

✅ Passed. All Quality Gates passed.

  • quality_gate_security_no_fs_load, bounds check memory_usage: 10/10 replicas passed. Gate passed.
  • quality_gate_security_no_fs_load, bounds check cpu_usage: 10/10 replicas passed. Gate passed.
  • quality_gate_security_mean_fs_load, bounds check cpu_usage: 10/10 replicas passed. Gate passed.
  • quality_gate_security_mean_fs_load, bounds check memory_usage: 10/10 replicas passed. Gate passed.
  • quality_gate_idle_all_features, bounds check total_bytes_received: 10/10 replicas passed. Gate passed.
  • quality_gate_idle_all_features, bounds check intake_connections: 10/10 replicas passed. Gate passed.
  • quality_gate_idle_all_features, bounds check memory_usage: 10/10 replicas passed. Gate passed.
  • quality_gate_idle, bounds check intake_connections: 10/10 replicas passed. Gate passed.
  • quality_gate_idle, bounds check total_bytes_received: 10/10 replicas passed. Gate passed.
  • quality_gate_idle, bounds check memory_usage: 10/10 replicas passed. Gate passed.
  • quality_gate_logs, bounds check missed_bytes: 10/10 replicas passed. Gate passed.
  • quality_gate_logs, bounds check intake_connections: 10/10 replicas passed. Gate passed.
  • quality_gate_logs, bounds check memory_usage: 10/10 replicas passed. Gate passed.
  • quality_gate_logs, bounds check total_bytes_received: 10/10 replicas passed. Gate passed.
  • quality_gate_security_idle, bounds check memory_usage: 10/10 replicas passed. Gate passed.
  • quality_gate_security_idle, bounds check cpu_usage: 10/10 replicas passed. Gate passed.
  • quality_gate_private_action_runner, bounds check memory_usage: 10/10 replicas passed. Gate passed.
  • quality_gate_metrics_logs, bounds check total_bytes_received: 10/10 replicas passed. Gate passed.
  • quality_gate_metrics_logs, bounds check memory_usage: 10/10 replicas passed. Gate passed.
  • quality_gate_metrics_logs, bounds check intake_connections: 10/10 replicas passed. Gate passed.
  • quality_gate_metrics_logs, bounds check missed_bytes: 10/10 replicas passed. Gate passed.
  • quality_gate_metrics_logs, bounds check cpu_usage: 10/10 replicas passed. Gate passed.

@brycekahle
brycekahle force-pushed the bryce.kahle/ebpf-manager-v083 branch from 4a70ad3 to 0f6d164 Compare August 26, 2026 20:58
@brycekahle

brycekahle commented Aug 26, 2026

Copy link
Copy Markdown
Member Author

/merge

@gh-worker-devflow-routing-ef8351

gh-worker-devflow-routing-ef8351 Bot commented Aug 26, 2026 •
edited
Loading

Copy link
Copy Markdown

View all feedbacks in Devflow UI.

2026-08-26 21:42:16 UTC ℹ️ Start processing command /merge

2026-08-26 21:42:22 UTC ℹ️ MergeQueue: Pull request is not mergeable yet

It will be processed automatically as soon as GitHub reports it as mergeable. View in MergeQueue UI.

  • Run /code blockers to see what is blocking it.
  • Run /remove to cancel it.

2026-08-26 22:11:11 UTC ℹ️ MergeQueue: merge request added to the queue

The expected merge time in main is approximately 5h (p90).

2026-08-26 22:48:42 UTC ℹ️ MergeQueue: This merge request was merged

@gh-worker-dd-mergequeue-cf854d
gh-worker-dd-mergequeue-cf854d Bot merged commit 8e15523 into main Aug 26, 2026
248 checks passed
@gh-worker-dd-mergequeue-cf854d
gh-worker-dd-mergequeue-cf854d Bot deleted the bryce.kahle/ebpf-manager-v083 branch August 26, 2026 22:48
@github-actions github-actions Bot added this to the 7.84.0 milestone Aug 26, 2026
github-actions Bot pushed a commit that referenced this pull request Aug 26, 2026
@gh-worker-dd-mergequeue-cf854d
update github.com/DataDog/ebpf-manager to v0.8.3 (#55262)
90e83b2 
<!--Please give us some feedback on your experience writing this PR ! https://app.datadoghq.com/forms/43db4c02-6837-400c-8083-692e141b1b88 !-->

### What does this PR do?

update `github.com/DataDog/ebpf-manager` to `v0.8.3`

### Motivation

Fix data race. See DataDog/ebpf-manager#285

### Describe how you validated your changes

### Additional Notes

Co-authored-by: bryce.kahle <bryce.kahle@datadoghq.com> 8e15523
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@mbertrone mbertrone mbertrone approved these changes

Assignees

No one assigned

Labels

changelog/no-changelog No changelog entry needed internal Identify a non-fork PR qa/done QA done before merge and regressions are covered by tests short review PR is simple enough to be reviewed quickly

Projects

None yet

Milestone

7.84.0

Development

Successfully merging this pull request may close these issues.

2 participants

@brycekahle @mbertrone